Types are automatically converted as shown in
table below:
ISaGRAF 3.x
ISaGRAF 4.x
Boolean
BOOL
Analog (integer)
DINT
Analog (real)
REAL
Timer
TIME
Message
STRING
Type conversion functions BOO, ANA, REAL, TMR,
MSG become ANY_TO_BOOL, ANY_TO_DINT, ANY_TO_REAL, ANY_TO_TIME,
ANY_TO_STRING in ISaGRAF PRO. These are automatically converted by
IAC tool. See below.
Defined words with local scope are not
considered by the migration tool. Use only global scope for defined
words.
IO wiring needs to be redone manually.
The generic "Operate" function proposed by
ISaGRAF 3.xx, and implemented by hardware manufacturers and
integrators, does not exist in ISaGRAF. Most of the times, Operate
calls are replaced by actual function calls by the integrator. You
need to adjust source code using the Operate function according to
the I/O convention proposed for ISaGRAF by the hardware
supplier.
ISaGRAF does not support conversion tables
such as defined in ISaGRAF 3.xx. You need to review the handling of
I/O channels in ISaGRAF after the converted application is
imported. A very popular use of conversion table is to define
scaling with a 2 point table. This can be easily replaced in
ISaGRAF by setting the gain and offset defined for each I/O
channel.
The use of conversion functions is not
automatically translated by the Application Converter. You need to
re-apply conversion functions to I/O channels in the ISaGRAF I/O
wiring tool, after the converted application is imported.
Library elements are not imported.Thus, please
import all IEC function or function blocks into your project before
following the procedure below.
Concerning IO boards, and "C" elements they
can be defined in a ISaGRAF project database using the tool TDBUILD
that generates a definition file that can then be imported into the
project with the File/Import/PLC definition command of the
workbench. See on-line help of TDBUILD.exe
ISaGRAF does not support SFC macro steps. The
Application Converter indicates in its report the SFC charts
including macro steps. The body of the macro step is kept by the
conversion. You need to re-draw the links between main chart and
macro steps using ISaGRAF PRO.
The "GSnnn(ProgName).X" and
"GSnnn(ProgName).T" statements can be used in
ISaGRAF 3.xx to refer to a step in another program. The use of such
statements in ISaGRAF 3.xx generates warning messages at build time
because those statements are not IEC compliant. ISaGRAF does not
support them. Instead, you must use global variables, forced in the
SFC chart and read in other POUs.
Notes:
The TDBuild tool is delivered with the workbench
and located in the Bin directory.
If you import the files generated by TDBuild into
an ISaGRAF PRO project, the definition of the concerned C elements
will be defined in the project database.
This tool produces also the C template files with
the ISaGRAF target format. These files can then be adapted and
compiled and linked in the ISaGRAF target environment.
To port your ISaGRAF application to an ISaGRAF project, please
follow the instructions below:
Launch IAC.exe located in the Bin directory of ISaGRAF
installation directory. IAC is for ISaGRAF Application
Converter.
Use the File / Open project command to select the directory
where your ISaGRAF 3 application is stored (c:\ISAWIN\Smp for
example for demo applications)
Do Build/Verify so that you can what instructions will not be
accepted in the ISaGRAF project. Then you have 2 solutions:
Correct the ISaGRAF3 application and restart from point 1
Correct the ISaGRAF application after this procedure has been
completed
Do Build/Build Exchange file. Enter information required by the
dialog box shown.
Open ISaGRAF workbench and open a project or create a new
project.
Use the command File / Import / Resource and follow
instructions. In the second dialog, you must select the file
generated by the IAC tool.
After that, you have at least to redo your IO wiring.
Do not hesitate to give us your feeb-back so that we can improve
the tools and/or the documentation.
Notes: